-
Notifications
You must be signed in to change notification settings - Fork 6.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Docker: replace the use of containerd_version with docker_containerd_version #8130
Docker: replace the use of containerd_version with docker_containerd_version #8130
Conversation
…version to avoid causing conflicts when bumping containerd_version
@cristicalin I'm not sure I get the idea here. If you are using docker then you can specify Edit: Ok this is linked to #8129 ? You want to be able to set containerd_version to 1.4.11 while keeping docker_containerd_version to 1.4.9 ? |
The problem comes from using In addition to this, setting the Splitting the two types of containerd deployments makes more sense to me but I'm open to other suggestions to ensure we don't break either deployment type and are still able to keep up to date with the upstreams or each docker and containerd. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: cristicalin, floryut The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/lgtm |
…version to avoid causing conflicts when bumping containerd_version (kubernetes-sigs#8130)
…version to avoid causing conflicts when bumping containerd_version (kubernetes-sigs#8130)
Avoid causing conflicts when bumping
containerd_version
when docker does not keep up with the latest containerd releases.What type of PR is this?
/kind bug
What this PR does / why we need it:
With the change of using containerd from upstream instead of the docker repos, we are now able to move faster than docker for the containerd runtime but we want to avoid breaking the docker deployment experience when bumping our default containerd version. As such I split the
containerd_version
into a dedicated deployment variable calleddocker_containerd_version
which is used when thecontainerd_manager
==docker
.Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?: